Skip to content

fix: align pom artifactId + README with JitPack publish coords (com.qtsurfer:api-client-java)#2

Merged
mrmx merged 1 commit into
mainfrom
fix/jitpack-artifactid
May 26, 2026
Merged

fix: align pom artifactId + README with JitPack publish coords (com.qtsurfer:api-client-java)#2
mrmx merged 1 commit into
mainfrom
fix/jitpack-artifactid

Conversation

@mrmx
Copy link
Copy Markdown
Contributor

@mrmx mrmx commented May 26, 2026

Summary

JitPack with the registered `com.qtsurfer` domain uses the GitHub repo name as the artifactId, NOT the pom ``. Verified empirically:

URL HTTP
`jitpack.io/v/com.qtsurfer/api-client.svg` 401 (no artifact)
`jitpack.io/v/com.qtsurfer/api-client-java.svg` 200 ✅

The pom said `api-client`; consumers can't actually pull that coord. Renaming to `api-client-java` makes the published name match the local `mvn install` name match the README snippets.

Changes

  • `pom.xml`: `api-client` → `api-client-java`
  • `README.md`: badge URL, top-of-page chips, Gradle line, "Maven Central (future)" line — all use `com.qtsurfer:api-client-java`
  • `README.md`: stale version `0.3.0` → `0.3.1` (matches current pom)

Test plan

  • Diff scope sanity: 2 files, 3 + 5 line changes total
  • CI green

JitPack with the registered com.qtsurfer domain uses the GitHub repo
name as the artifactId, not pom <artifactId>. Empirical check:
  https://jitpack.io/v/com.qtsurfer/api-client.svg      → 401
  https://jitpack.io/v/com.qtsurfer/api-client-java.svg → 200

The pom said api-client; consumers can't actually pull that coord.
Renaming to api-client-java makes the published name match the local
mvn install name match the README snippets. Side fix: README still
showed version 0.3.0, bumped to 0.3.1 to match current pom version.
@mrmx mrmx merged commit 4ba5c07 into main May 26, 2026
4 checks passed
@mrmx mrmx deleted the fix/jitpack-artifactid branch May 26, 2026 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant